Skip to content

Point to artifact verification from the security policy - #8

Merged
alexander-yevsyukov merged 1 commit into
masterfrom
verifying-artifacts
Oct 1, 2026
Merged

alexander-yevsyukov merged 1 commit into
masterfrom
verifying-artifacts

Conversation

@alexander-yevsyukov

Copy link
Copy Markdown
Contributor

Part 2 of the Security section rollout. The site side is live: SpineEventEngine/documentation#88 and SpineEventEngine/SpineEventEngine.github.io#554.

What changed in SECURITY.md

  • New section, "Verifying our artifacts", after "Third-party components". It's a pointer with no commands:

    • the artifacts we publish to Maven repositories carry SLSA build provenance;
    • what checking it proves (built by us from a protected branch, unchanged since), and that it doesn't mean the artifact is free of vulnerabilities;
    • older artifacts may carry no provenance, or provenance at a lower level.

    The full instructions live at https://spine.io/docs/security/verifying-artifacts/. This follows the pattern of Argo CD, Kubernetes and Kyverno: the site holds the procedure, and SECURITY.md points to it.

  • CVD Policy link now points to its canonical URL, https://spine.io/docs/security/cvd-policy/. The old /cvd-policy/ keeps redirecting there for links elsewhere.

Why it's worded this way

  • It says "artifacts we publish to Maven repositories", not "Spine", so it stays true in repositories that publish nothing. This file is the default SECURITY.md for every repository of the organization.
  • It ties "Build Level 3" to the mechanism rather than presenting it as a certification.
  • It covers legacy artifacts, so someone whose older JAR fails to verify isn't alarmed.

"From a protected branch" holds for the repositories checked: master of .github and base-libraries has a ruleset that blocks deletion and force-pushes and requires pull requests.

Checks

  • All three link targets return 200.
  • GitHub renders the new section, with all references resolved.
  • The Security policy page on spine.io renders this file at build time; Hugo's Goldmark renders the new section the same way, and it appears in the page's table of contents.

After merging

Run the spine.io Deploy to GitHub Pages workflow by hand (Run workflow on master), so https://spine.io/docs/security/policy/ picks up this version without waiting for the next commit there.

🤖 Generated with Claude Code

Add a "Verifying our artifacts" section. It says that the artifacts we
publish to Maven repositories carry SLSA build provenance, what checking
it proves and what it doesn't, and that older versions may carry none.
The command and the details live on spine.io, at Documentation >
Security > Verifying artifacts, which the section links to.

Also point the CVD Policy link to its new address,
https://spine.io/docs/security/cvd-policy/. The old one redirects there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-01T14:15:11.250889Z ffe516d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@alexander-yevsyukov
alexander-yevsyukov merged commit f208d5c into master Oct 1, 2026
@alexander-yevsyukov
alexander-yevsyukov deleted the verifying-artifacts branch October 1, 2026 14:30
@alexander-yevsyukov
alexander-yevsyukov restored the verifying-artifacts branch October 1, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants